QuickVPN Client v1.2.11 Release Note

7/1/2008

Issues Fixed:

1. Fixed a QuickVPN Connectivity issue, where QuickVPN Client running on Vista with 
   a wireless LAN adapter cannot connect to a remote QuickVPN router.
2. When QuickVPN Client fails to establish a tunnel with WRV200, the client 
   will try to detect whether the Ping (ICMP) is blocked or the IKE negotiation
   (on UDP port 500 or 4500) is blocked, and log messages in the log.txt accordingly.


Known Issues:
     
1. QuickVPN Client v1.2.5 or newer, when running on Windows Vista, cannot 
   connect to RVS4000 nor WRVS4400N when Vista is behind a Network Address 
   Translation (NAT) device. The problem does not occur to QuickVPN Client 
   running on Windows XP or 2000. This was caused by the change in Windows OS
   behavior. For more information, please see    
   http://support.microsoft.com/kb/944335/en-us.

2. Windows Firewall needs to be enabled on Windows Vista in order for QuickVPN
   Client to function properly. This is due to the fact that IPSec service on 
   Vista is disabled when Windows Firewall is disabled. Some third-party    
   firewall will disable the Windows Firewall, which will cause QuickVPN 
   to fail.   

3. Users need to have the administrative rights in order to use QuickVPN Client. 
   This is a constraint posed by the Windows operating systems.

4. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always
   dropped by the Firewall when the Firewall is enabled. The issue will cause 
   the QuickVPN Client not being able to establish a tunnel with the remote    
   QuickVPN Server successfully. Microsoft has released a patch to fix this 
   issue. Once you install the patch, the issue should be resolved. 
   http://support.microsoft.com/kb/889527/en-us

5. QuickVPN tunnels do not pass NetBIOS broadcast packets. This may create a 
   problem when users want to search computers by names or to browse the network 
   neighborhood on Windows Explorer. Users can use a LMHOSTS file to work around 
   this issue. More information can be found at 
   http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_qxqq.mspx?mfr=true

-----------------------------------------------------------------------------------------
QuickVPN Client v1.2.8 Release Note

1/4/2008

Issues Fixed:

1. Fixed the issue that QuickVPN Client on Windows Vista cannot work properly 
   when the Server Address field is a DDNS domain name.
2. Upon uninstalling the QuickVPN Client, the install directory will be 
   removed completely. 
3. QuickVPN Client will log more messages in the log.txt file to ease 
   troubleshooting.

Known Issues:
     
1. QuickVPN Client v1.2.5 or newer, when running on Windows Vista, cannot 
   connect to RVS4000 nor WRVS4400N when Vista is behind a Network Address 
   Translation (NAT) device. The problem does not occur to QuickVPN Client 
   running on Windows XP or 2000. This was caused by the change in Windows OS
   behavior. For more information, please see    
   http://support.microsoft.com/kb/944335/en-us.

2. Windows Firewall needs to be enabled on Windows Vista in order for QuickVPN
   Client to function properly. This is due to the fact that IPSec service on 
   Vista is disabled when Windows Firewall is disabled. Some third-party    
   firewall will disable the Windows Firewall, which will cause QuickVPN 
   to fail.   

3. Users need to have the administrative rights in order to use QuickVPN Client. 
   This is a constraint posed by the Windows operating systems.

4. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always
   dropped by the Firewall when the Firewall is enabled. The issue will cause 
   the QuickVPN Client not being able to establish a tunnel with the remote    
   QuickVPN Server successfully. Microsoft has released a patch to fix this 
   issue. Once you install the patch, the issue should be resolved. 
   http://support.microsoft.com/kb/889527/en-us

5. QuickVPN tunnels do not pass NetBIOS broadcast packets. This may create a 
   problem when users want to search computers by names or to browse the network 
   neighborhood on Windows Explorer. Users can use a LMHOSTS file to work around 
   this issue. More information can be found at 
   http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_qxqq.mspx?mfr=true

---------------------------------------------------------------------------------------------------------------------------
QuickVPN Client v1.2.6 Release Note

9/30/2007

Issues Fixed:

1. QuickVPN Client v1.2.5 can support Windows Vista machines that do not have 
   QuickVPN Client v1.0.x installed previously. If a Vista machine has prior 
   QuickVPN Client such as v1.0.39 installed, QuickVPN Client v1.2.5 cannot    completely uninstall the prior version. This release fixed the issue by 
   cleaning up the Windows Registry associated with QuickVPN Client during the 
   uninstallation.

Known Issues:
     
1. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always dropped by the Firewall when the Firewall is enabled. The issue will cause the QuickVPN Client not being able to establish a tunnel with the remote QuickVPN Server successfully. Microsoft has released a patch to fix this issue. Once you install the patch, the issue should be resolved. 
http://support.microsoft.com/kb/889527/en-us

2. QuickVPN Client v1.2.5 or newer, when running on Vista, has an interop issue with RVS4000 firmware v1.1.09 and v1.1.11 (beta). The interop issue was fixed by firmware v1.1.13 (beta).

3. QuickVPN Client v1.2.5 or newer, when running on Vista, has an interop issue with WRVS4400N firmware v1.0.12, v1.0.13 and v1.0.15 (beta). The interop issue was fixed by firmware v1.0.16.

4. Users need to have the administrative rights in order to use QuickVPN Client. This is a constraint posed by the Windows operating systems.

5. QuickVPN tunnels do not pass NetBIOS broadcast packets. This may create a problem when users want to search computers by names or to browse the network neighborhood on Windows Explorer. Users can use a LMHOSTS file to work around this issue. More information can be found at 
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_qxqq.mspx?mfr=true


---------------------------------------------------------------------------------------------------------------------------
QuickVPN Client v1.2.5 Release Note

7/27/2007

Enhancements:

1. Support Windows Vista in addition to Windows XP/2000.

2. Updated the OpenSSL library (libeay32.dll and ssleay32.dll) from v0.9.8c to v0.9.8d due to some known vulnerability issues. For more information, please visit http://www.openssl.org/

3. Fixed an issue with the Status Window showing Tunnel Connected but the tunnel is in fact not established. With v1.1.2 (or newer) QuickVPN client will ping the LAN IP address of the remote QuickVPN server before it shows the tunnel is connected. If the client cannot successfully ping the router's LAN IP within 1 minute, it will pop up a message, asking if the user wants to wait for the connection. Users can choose to wait or quit. This also requires newer firmware on the QuickVPN server side. Currently only RVS4000 v1.1.x and WRV200 v1.0.29 (or newer) support this.

4. The Help page has been updated to include some descriptions of the status and error messages.

5. Hide the passwords logged in wget_error.txt and wget_stop_error.txt.

Known Issues:
     
1. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always dropped by the Firewall when the Firewall is enabled. The issue will cause the QuickVPN Client not being able to establish a tunnel with the remote QuickVPN Server successfully. Microsoft has released a patch to fix this issue. Once you install the patch, the issue should be resolved. 
http://support.microsoft.com/kb/889527/en-us

2. QuickVPN Client v1.2.5 has an interop issue with RVS4000 firmware v1.1.09 and v1.1.11 (beta). However, QuickVPN Client v1.2.5 does work with RVS4000 firmware 1.0.x. New firmware will be released to fix the interop issue. 

3. QuickVPN Client v1.2.5 has an interop issue with WRVS4400N firmware v1.0.12, v1.0.13 and v1.0.15 (beta). New firmware will be released to fix the interop issue.

4. Users need to have the administrative rights in order to use QuickVPN Client. This is a constraint posed by the Windows operating systems.

---------------------------------------------------------------------------------------------------------------------------

QuickVPN Client v1.1.0 Release Note

2/05/2007

1. To enhance the security of QuickVPN, this release of QuickVPN client will verify whether the SSL certificate presented by the remote QuickVPN server is trustable. Currently the client only trusts the certificates that are present in the installation directory of the QuickVPN client. Users of QuickVPN client need to get the certificate of the QuickVPN router from the administrator and store it in the QuickVPN client installation directory, e.g. C:\Program Files\Linksys\Linksys VPN Client\. This way the QuickVPN client will not be deceived by a hacker in the middle and connect to a hostile computer. With QuickVPN client v1.1.0, when the client encounters a certificate that is not trusted, the client will pop up an warning message, suggesting the user quit the connection attempt. For backward compatibility with older QuickVPN servers, users are allowed to choose not to quit the connection attempt and establish a tunnel.   

2. Added a configurable port for QuickVPN client to connect with the remote QuickVPN server. The port is defaulted to Auto, in which mode the QuickVPN client will try to connect to the remote QuickVPN server using port 443. If not successful, the client will change to port 60443. This could happen when the remote QuickVPN server has enabled port forwarding on port 443, or when the remote QuickVPN server does not use port 443 for QuickVPN, e.g. WRV200.
